AR V300R023SPH150

The DDR online isolation function is disabled by default.
The xDSL firmware of a device cannot be upgraded or downgraded.
When the log buffer is full, logs cannot be automatically dumped.
The local device is connected to a remote device through an optical module. After the interface where the optical module is installed goes Up and then is shut down, the interface indicator is not off.
After a specific optical module is installed on a device, the device cannot register with the controller.
When the idle-timeout command is executed through a .bat script, the command does not take effect.
After an Ethernet cable of a network interface is manually removed and then inserted, the interface goes Up, but traffic cannot be forwarded.
When the local breakout, URL filtering, and firewall services are configured in an SD-WAN scenario, the centralized Internet access configuration does not take effect for some traffic.
After two IPv6 links for local Internet access are configured for a device through the controller, an attempt is made to disable one of the links. However, this configuration fails to be delivered.
When NAT is configured on multiple uplink interfaces of a device and the NAT flow log function is enabled, the device restarts.
Packet loss occurs when the Ethernet cable of the management interface is manually removed and inserted.
When the NAT service is configured on a device and ESP and AH packets are forwarded on the device, services are interrupted.
LTE cellular interfaces cannot be used for deployment through the registration query center.
When SSH and RADIUS authentication are configured and a user repeatedly logs in to a device, resources on the device are abnormally occupied.
In the SD-WAN dual-gateway scenario, packet loss lasts for a long time during traffic switching upon a WAN interface fault.
When a device is managed by the controller and IPv6 addresses are configured, full configurations fail to be delivered.
After a device is restarted, the controller fails to deliver LTE configurations.
When a device connects to the network through LTE, the latency is unstable.
After the dns-list command is delivered through YANG, the IP address sequence in the configuration on the device is different from that in the delivered configuration.
After an IPv6 BFD connection is established, the connection is interrupted unexpectedly.
The number of STAs that can connect to a device functioning as a Fat AP is increased.
In an SD-WAN scenario, service traffic between branches fails to be forwarded.
In an SD-WAN scenario, keepalive packets of an EVPN tunnel are preferentially forwarded through a protocol queue by default.
After the IPv6 or IPv4 address family of a VPN instance is deleted, the VPN redirection function does not take effect.
After NAT is configured, service traffic fails to be forwarded.
In the SD-WAN scenario with active and standby hub sites, when traffic steering in LB mode is configured for branch sites and a fault occurs at the LAN side of a hub site, services are interrupted for a long time.
In an SD-WAN underlay IPv6 scenario, an error is reported when a CPE is unbound from an RR site.
In an SD-WAN scenario, when a device has an LTE link and a physical link for registration and the physical link is disconnected, no link alarm is reported.
A device restarts when reporting a large amount of performance data.
When route flapping occurs, traffic fails to be forwarded on the DSVPN network.
When a large number of links and SPR policies are deployed in an SD-WAN scenario and the global coloring rule configuration is modified on the controller, the device restarts unexpectedly.
When an LDP session is established for the L2VPN service and another LDP session flaps, the L2VPN service is interrupted.
When forcible NAT traversal is configured for IPsec-protected traffic on a device, the device cannot interconnect with a non-Huawei device.
Multiple PKI certificates fail to be updated through SCEP.
The device configuration restoration performance is optimized in SD-WAN scenarios.
When a device functions as a PD client and connects to a third-party DHCPv6 server, the prefix is not updated in case of interface status changes.
After TCP FPM is configured on a device, the device restarts.
TNP information cannot be reflected through BGP.
After controller information is configured for a device on the web system and the device is restarted, the controller configuration is lost.
The diagnosis capabilities in SD-WAN service scenarios are insufficient and need to be enhanced.
In an SD-WAN scenario, reading interface information on the device management page of the controller times out.
In a dynamic tunnel scenario, events are repeatedly reported upon link switching triggered by intelligent traffic steering.
The display cellular0/0/0 all command output is added to the output of the one-click diagnostic information collection command display diagnostic-information.